Selective Prioritization of Voice Over Data

ABSTRACT

Systems, methods, and computer-readable media are described herein for allowing a user or a service provider to selectively prioritize voice communications over data communications. By selectively prioritizing voice communications over data communications, the number of dropped calls in the mobile telecommunications network can be significantly reduced.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/117,792, filed May 27, 2011, now allowed, which is incorporatedherein by reference in its entirety.

BACKGROUND

This application relates generally to providing voice and datacommunication in a mobile telecommunications network and, moreparticularly, to selectively prioritizing voice communications over datacommunications in a mobile telecommunications network.

Some mobile telecommunications networks, such as those based uponUniversal Mobile Telecommunications System (“UMTS”), utilize a bearerservice called a radio access bearer (“RAB”) to establish voice and/ordata connections between a mobile device and a core network. UMTSpermits the simultaneous transmission of voice and data content over aspecial-purpose RAB called a multi-RAB (also called an “mRAB”). When asubscriber is using their mobile device for voice communications and thenetwork has data to transmit to the mobile device, the network and themobile device jointly establish an mRAB to support simultaneoustransmission of voice and data content. Similarly, an mRAB can beestablished if the subscriber takes actions to initiate a data transfer,such as by initiating a download or launching an application that relieson a data connection to populate its content.

Communications over an mRAB are not without complications. For example,a mobile device using an mRAB for voice and data communications isrequired to supply sufficient uplink transmit power to support both thevoice and data components of the mRAB. Under some conditions, such aswhen the mobile device is approaching the edge of network coverage, themobile device may use all or at least a majority of its available uplinktransmit power to maintain acceptable voice quality for a voice call.When an mRAB is invoked to transfer data, the radio link budget isimpaired by several decibels, at which point the mobile device can nolonger support both the voice and data components. If either componentfails, the mRAB is torn down, resulting in a dropped call. Thesubscriber is likely unaware of the underlying mechanisms that forcedtheir call to be dropped, particularly for scenarios in which abackground service, such as an email push, forced establishment of themRAB while the subscriber was on the call.

Recent performance trends in UMTS-based networks have shown that thenumber of dropped voice calls due to mRAB connections can be severaltimes the number of dropped voice calls when a voice-only RAB is used.Mobile network operators may want to promote their competitive advantagein offering wireless service that allows simultaneous voice and data. Indoing so, however, these mobile network operators may also exacerbatethe aforementioned problems leading to a higher frequency of droppedcalls and, as a result, reduced consumer confidence, bad press,decreased subscriber retention, and revenue loss.

SUMMARY

Computer readable media are described herein for allowing a user or aservice provider to selectively prioritize voice communications overdata communications. By selectively prioritizing voice communicationsover data communications, the number of dropped calls in the mobiletelecommunications network can be significantly reduced.

According to one aspect presented herein, a computer storage medium hascomputer readable instructions stored thereupon that, when executed by amobile device, cause the mobile device to receive a selection of a voiceprioritized option and conditionally deny data access in response toreceiving the selection of the voice prioritized option. In someembodiments, conditionally denying data access includes conditionallylimiting data access. For example, data access may be limited bychanging the data rate available to the mobile device and/or allowingonly certain types of data. For example, text or other low-capacity datamay be allowed while video content or other high-capacity data isdenied. Also, for example, data access may be limited by location suchthat if the mobile device is located in a certain location, the mobiledevice is limited data access to all or some data types.

According to another aspect presented herein, a computer storage mediumhas computer readable instructions stored thereupon that, when executedby a mobile device, cause the mobile device to receive a value for avoice priority setting from a server, store the value for the voicepriority setting, and conditionally deny data access in accordance withthe value stored for the voice priority setting.

According to another aspect presented herein, a computer storage mediumhas computer readable instructions stored thereupon that, when executedby a mobile device, cause the mobile device to establish a voice call,measure a statistic at the mobile device during the call, tear down thevoice call, and report the statistic to a remote server.

Other systems, methods, and/or computer readable media according toembodiments will be or become apparent to one with skill in the art uponreview of the following drawings and detailed description. It isintended that all such additional systems, methods, and/or computerprogram products be included within this description, be within thescope of this disclosure, and be protected by the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a network architecture diagram schematically illustrating anexemplary operating environment for implementing various embodimentspresented herein.

FIG. 2 is a flow diagram showing aspects of a method for selectivelyestablishing an mRAB, according to an exemplary embodiment.

FIG. 3 is a flow diagram showing aspects of another method forselectively establishing an mRAB, according to an exemplary embodiment.

FIG. 4 is a flow diagram showing aspects of a method for selectivelyestablishing an mRAB in response to a user-initiated data request,according to an exemplary embodiment.

FIG. 5 is a flow diagram showing aspects of a method for selectivelyestablishing an mRAB in response to a network-initiated data request,according to an exemplary embodiment.

FIG. 6 is a flow diagram showing aspects of another method forselectively establishing an mRAB, according to an exemplary embodiment.

FIG. 7 is a flow diagram showing aspects of a method for operating aserving general packet radio service support node to selectivelyestablish an mRAB, according to an exemplary embodiment.

FIG. 8 is a flow diagram showing aspects of a method for operating aradio network controller to selectively establish an mRAB, according toan exemplary embodiment.

FIG. 9 is a flow diagram showing aspects of a method for notifying auser that a data connection is currently unavailable, according to anexemplary embodiment.

FIG. 10 is a flow diagram showing aspects of a method for providing auser override option if the establishment of an mRAB is denied,according to an exemplary embodiment.

FIG. 11 is a flow diagram showing aspects of a method for prioritizingvoice calls over data based upon a selection of a voice priority option,according to an exemplary embodiment.

FIGS. 12A-12C are graphical user interfaces (“GUIs”) illustrating ameans for selecting a voice priority option, according to variousexemplary embodiments.

FIG. 13 is a GUI illustrating voice priority settings, according to anexemplary embodiment.

FIG. 14 is a flow diagram showing aspects of a method for remotelyconfiguring voice priority settings, according to an exemplaryembodiment.

FIG. 15 is a flow diagram showing aspects of a method for reportingmeasured statistics to a remote server, according to an exemplaryembodiment.

FIG. 16 is a mobile device architecture diagram illustrating anexemplary device hardware and software architecture for a mobile devicecapable of implementing aspects of the embodiments presented herein.

FIG. 17 is a computer architecture diagram illustrating an exemplarycomputer hardware and software architecture for a computing systemcapable of implementing aspects of the embodiments presented herein.

DETAILED DESCRIPTION

The following detailed description is directed to various aspects forselectively prioritizing voice calls over data communications in amobile telecommunications network. While the subject matter describedherein may be presented, at times, in the general context of programmodules that execute in conjunction with the execution of an operatingsystem and application programs on a computer system, those skilled inthe art will recognize that other implementations may be performed incombination with other types of program modules. Generally, programmodules include routines, programs, components, data structures, andother types of structures that perform particular tasks or implementparticular abstract data types. Moreover, those skilled in the art willappreciate that the subject matter described herein may be practicedwith other computer system configurations, including hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and the like.

Referring now to FIG. 1, aspects of a network 100 for variousembodiments presented herein will be described. The network 100 isillustrated and described in context of a Universal MobileTelecommunications System/Universal Mobile Telephone System (“UMTS”)network capable of providing simultaneous voice and data communications.Although various aspects are disclosed in this particular context, thoseskilled in the art will appreciate the applicability of many of thedisclosed aspects to other mobile telecommunications technologies thatsupport simultaneous voice and data communications, and/or technologiessuch as High-Speed Packet Access (“HSPA”) and HSPA+ that enhance orbuild upon the capabilities of UMTS by providing higher data transferrates or other features. It is contemplated that the network 100 may notinclude all of the network elements shown in FIG. 1, may include othernetwork elements that are not explicitly shown in FIG. 1, may includemultiples of the network elements that are explicitly shown in FIG. 1,and/or may utilize an architecture completely different than that shownin FIG. 1.

The network 100 includes a mobile communications device (“MD”) 102, suchas a cellular telephone or a computer configured with an integrated oran external, removable UMTS access component that facilitates wirelesscommunication with the network 100. In some embodiments, the UMTS accesscomponent is a cellular telephone that is in wired or wirelesscommunication with the computer to facilitate a tethered data connectionto the network 100. In other embodiments, the UMTS access componentincludes a wireless transceiver to send and receive data from thenetwork 100 and a universal serial bus (“USB”) or another communicationinterface for connection to the computer to enable tethering. In anycase, the MD 102 is configured to wirelessly communicate with a UMTSTerrestrial Radio Access Network (“UTRAN”) 104 via a Uu radio interface,as shown in the illustrated embodiment. An exemplary device architectureof the MD 102 is illustrated and described herein below with referenceto FIG. 16.

The UTRAN 104 is in communication with a circuit-switched core network(“CS CN”) 106 and a packet-switched core network (“PS CN”) 108 via anIu-CS interface and an Iu-PS interface, respectively. The CS CN 106 isalso in communication with a circuit network 110, such as a PublicSwitched Telephone Network (“PSTN”), an Integrated Services DigitalNetwork (ISDN), or other circuit-switched network. The PS CN 108 is alsoin communication with a packet network 112, such as an internet, anintranet, or other packet-switched network.

The packet network 112 is also in communication with a server 114. Theserver 114 is configured to provide data content to the PS CN 108 fordelivery to the MD 102 over the UTRAN 104. The content provided by theserver 114 may be content requested and subsequently downloaded by theMD 102 (e.g., a data pull operation) or may be content pushed to the MD102. The server 114 may host content associated with a particularwebsite and/or a particular service. Exemplary services that may beprovided by the server 114 include an email service, a social networkingservice, a professional networking service, a news service, an onlinegaming service, an audio or video streaming service, an applicationsoftware download service, a music or video download service, a webapplication service, or any other type of service that provides contentto mobile devices.

Referring again to the UTRAN 104, as illustrated, the UTRAN 104 includesa node B 116 and a radio network controller (“RNC”) 118. The node B 116includes one or more transceivers for transmission and reception of dataacross the Uu radio interface. The node B 116 is the terminating node ofthe UTRAN 104 for the Uu radio interface. The node B 116 is incommunication with the RNC 118 via an Iub interface. The RNC 118 isconfigured to allocate radio resources to the MD 102, apply codes todescribe channels in accordance with Wideband Code Division MultipleAccess (“W-CDMA”) protocol, and control handovers between the node B 116and one or more other node Bs (not shown). The RNC 118 also acts aconcentrator, so that many different low capacity connections to thenode B 116 become reduced to a smaller number of connections towards theCS CN 106 and the PS CN 108 via the Iu-CS and Iu-PS interfaces,respectively.

The UTRAN 104 and, particularly, the RNC 118 communicates with the CS CN106 via a mobile switching center (“MSC”) 120 using the Iu-CS interface.The MSC 120 is configured to function as a telecommunications switch forvoice calls in the network 100. The MSC 120 is in communication withlocation databases, such as a visiting location register (“VLR”) and ahome location register (“HLR”) 122. The VLR may be logically associatedwith the MSC 120, as illustrated, or may be provided as a separatenetwork element in communication with the MSC 120. The VLR is a databaseconfigured, in part, to store all subscriber data that is required forcall processing and mobility management for mobile subscribers that arecurrently located in an area controlled by the MSC 120. The HLR 122 isin communication with the MSC 120 and the VLR via a C interface and a Dinterface, respectively (shown together for convenience as a C/Dinterface). The HLR 122 is a database configured, in part, to providerouting information for mobile-terminated calls and various messagingcommunications. The HLR 122 is also configured to maintain subscriberdata that is distributed to the relevant VLR or elements of the PS CN108 through an attach process and to perform mobility managementprocedures, such as location area and routing area updates.

The HLR 122 may be logically associated with an authentication center(not shown) that is configured to authenticate a universal subscriberidentity module (“USIM”, also not shown) of the MD 102 when the MD 102attempts to connect to the network 100, such as during a power-onprocedure. Once authenticated, the HLR 122 is permitted to manage theUSIM and services provided to the MD 102. The authentication center isalso configured to generate an encryption key that is used to encryptall wireless communications between the MD 102 and the core networks106, 108.

The MSC 120 is also in communication with a gateway MSC (“GMSC”) 124 viaa B interface. The HLR 122 is in communication with the GMSC 124 via a Cinterface to obtain routing information for mobile-terminated callsoriginating from fixed network devices, such as landline telephonesoperating via the circuit network 110. The GMSC 124 is configured, inpart, to provide an edge function within the CS CN 106 to the circuitnetwork 110. In particular, the GMSC 124 is configured to terminatesignaling and traffic from the circuit network 110 and convert thesignaling and traffic to protocols employed by the CS CN 106. The GMSC124 may also provide gateway functions of the network 100 to anotherpublic land mobile network (“PLMN”, not shown).

The CS CN 106 is in communication with the PS CN 108 via the MSC 120 andthe HLR 122. In particular, the MSC 120 and the HLR 122 are incommunication with a serving General Packet Radio Service (“GPRS”)support node (“SGSN”) 126 via a Gs interface and a Gr interface,respectively. The SGSN 126 records and tracks the location of the MD 102in the network 100 and provides security and access control functionsfor packet-switched data connections within the network 100. The SGSN126 is in communication with the RNC 118 via the Iu-PS interface and agateway GPRS support node (“GGSN”) 128 via a Gn interface. The SGSN 126may also provide gateway functions of the PS CN 108 to another PLMN (notshown) via a Gp interface (also not shown).

The GGSN 128 is configured, in part, to provide an edge routing functionto the packet network 112 via a Gi interface. The GGSN 128 is configuredto receive data from the packet network 112 and provide it to the SGSN126 for delivery to the MD 102 over the UTRAN 104. The GGSN 128 alsoprovides firewall and filtering functionality for the PS-CN 108.

The CS CN 106, the UTRAN 104, and the MD 102 are configured to jointlynegotiate the establishment of a voice-only RAB (“vRAB”), for example,to facilitate voice communications between the MD 102 and anotherdevice. In some embodiments, a vRAB is established in response to amobile-initiated or a mobile-terminated call directed to or receivedfrom another device (not shown) operating within the network 100,another PLMN, or the circuit network 110. In any case, a vRAB may beestablished according to known vRAB establishment procedures, afterwhich voice communications between the MD 102 and the other device canbe exchanged, at least in part, over the vRAB. It is also contemplatedthat the vRAB may be configured to facilitate a conference call, whereinthe MD 102 is one of three or more devices participating in theconference call.

The PS CN 108, the UTRAN 104, and the MD 102 are configured to jointlynegotiate the establishment of a data-only RAB (“dRAB”), for example, tofacilitate data communications between the MD 102 and the server 114.The dRAB may be established according to known dRAB establishmentprocedures in response to a pull or push operation initiated by the MD102 or the server 114. Data communications between the MD 102 and theserver 114 can then be exchanged, at least partially, over the dRAB. Theinitiation of a push or pull operation by the MD 102 or the server 114is referred to herein, at times, as a data request. Generally, though, adata request is any message sent by an entity of the network 100 toanother entity of the network 100 in an attempt to access or deliverdata content.

The CS CN 106, the PS CN 108, the UTRAN 104, and the MD 102 are alsoconfigured to jointly negotiate the establishment of a multi-RAB(“mRAB”), for example, to facilitate voice communications between the MD102 and another device, and to facilitate data communications betweenthe MD 102 and the server 114. In some embodiments, an mRAB isestablished during a voice session occurring over a vRAB. In theseembodiments, after the mRAB is established, the voice session istransferred to the mRAB and the vRAB is torn down. A data session canthen be simultaneously conducted with the voice session over the mRAB.After the data session ends, a new vRAB may be established and the voicesession may be transferred to the new vRAB. Alternatively, the voicesession remains on the mRAB until completion.

In other embodiments, an mRAB is established during a data sessionoccurring over a dRAB. In these embodiments, after the mRAB isestablished, the data session is transferred to the mRAB and the dRAB istorn down. A voice session can then be simultaneously conducted with thedata session over the mRAB. After the data session ends, a new dRAB maybe established and the data session may be transferred to the new dRAB.Alternatively, the data session remains on the mRAB until completion.

Data requests originating from the MD 102 may be device-initiated oruser-initiated. In some embodiments, a device-initiated data request isa data request generated automatically by the MD 102 in response toinstructions received from an application residing on the MD 102. Insome embodiments, the MD 102 receives no direct user input through theapplication or otherwise to prompt generation of the data request. Inother embodiments, the MD 102 receives indirect user input, such as viapreference settings or other set and forget type settings, from a userof the MD 102. These settings may include, but are not limited to, thefrequency by which an application requests a data connection to downloadcontent. A user may desire to establish such a setting to mitigate datausage by the application, thereby potentially reducing data usage costs.The frequency by which the application requests a data connection todownload content may alternatively be set by the application developer,the mobile network operator providing the network 100, another mobilenetwork operator, another party, or another entity.

In some embodiments, a user-initiated data request is a data requestgenerated by the MD 102 in response to a direct user input. In someembodiments, a direct user input is a user input that causes anapplication to request a data connection. For example, a user may launchan application that at least temporarily requires a data connection. Inthis example, the application may require the data connection to searchfor available updates, download updates, download content for userconsumption, or otherwise use the data connection to provide somefunctionality to the user without the user providing an input in excessof launching the application. As an additional example, a user maylaunch an application that only requires a data connection for aparticular feature or mode within the application, such as a gameapplication that does not require a data connection for some features(e.g., single player modes, menu navigation, etc.) but requires a dataconnection for other features (e.g., multiplayer modes, to downloadoptional updates, to download optional additional content, etc.). Otherexamples of user inputs that would prompt an application to request adata connection include, but are not limited to, a search query withinan application (e.g., a web browser, an email client, an applicationstore, a music or video store, etc.), a user-initiated data pull thatprompts the application to initiate a download operation, a web pagerefresh, an email refresh, an audio or video streaming request, amultimedia messaging service (“MMS”) operation, and the like.

In some embodiments, data requests originating from the network 100include an action taken by an entity external to the MD 102 to invoke anoperation on the MD 102 that at least temporarily requires a dataconnection. For example, data requests originating from the network 100may originate from the GGSN 128 in response to the GGSN 128 receivinginstructions from the server 114 to deliver content to the MD 102 inaccordance with a data push operation. The server 114 may be configuredto push any type of content to the MD 102.

Regardless of the origin of the data request (i.e., the MD 102 or anentity external to the MD 102 within the network 100), in someembodiments, the data request includes a packet data protocol (“PDP”)message used during a PDP activation procedure between the MD 102 andthe PS CN 108 as a step towards creation of a dRAB or an mRAB dependingupon the scenario. In particular, the data request, in some embodiments,includes a PDP context activation request (i.e., an Activate PDP Contextmessage). For network-initiated data requests, a PDP context activationrequest is generated by and sent from the GGSN 128 to the SGSN 126 as aninitial operation towards the creation of a PDP context between the MD102 and the SGSN 126. For device-initiated or user-initiated datarequests, a PDP context activation request is generated by and sent fromthe MD 102 to the SGSN 126 towards the creation of a PDP context betweenthe MD 102 and the SGSN 126. For either scenario, after a PDP context isestablished between the MD 102 and the SGSN 126, a RAB (e.g., a dRAB oran mRAB) is established according to RAB establishment procedures. EachPDP context has its own RAB (between the MD 102 and the SGSN 126) andtunnel (between the SGSN 126 and the GGSN 128). Other details regardingthe establishment of a PDP context and a RAB, particularly the messagingthat occurs between elements of the network 100 during a PDP contextactivation sequence and a RAB establishment procedure, are known tothose skilled in the art and are beyond the scope of this disclosure.

In the illustrated embodiment of FIG. 1, the MD 102, the RNC 118, andthe SGSN 126 each have an application program module associatedtherewith. In particular, the MD 102 is associated with an MDapplication 130 (also referred to herein at times as “the mRAB decisionapplication 130”), the RNC 118 is associated with an RNC application132, and the SGSN 126 is associated with an SGSN application 134. Insome embodiments, the mRAB decision application 130 of the MD 102 isconfigured to perform operations towards a determination of whether anmRAB should be established, as described in greater detail herein, forexample, with reference to FIGS. 2-6. In some embodiments, the MDapplication 130 is configured to allow a user to prioritize voice overdata during a voice call. This is described in greater detail hereinwith reference to FIG. 11. In some embodiments, the MD application 130is configured to receive instructions from a remote server specifyingthe conditions under which voice prioritization should take place. Thisis described in greater detail herein with reference to FIG. 14. In someembodiments, the MD application 130 includes a measurement applicationto conduct measurement described herein below with reference to FIG. 15.Other embodiments of the MD application 130 are described herein.

In some embodiments, the RNC application 132 is configured to hold adata request received from the SGSN 126, prompt the SGSN 126 to bufferdata associated with the data request, and retry transmission of thedata request to the MD 102 based upon a retry interval, as described ingreater detail herein, for example, with particular reference to FIG. 8.In some embodiments, the SGSN module 134 is configured to delegate aretry interval by which the SGSN 126 should retry attempts to send datareceived from the GGSN 128 to the MD 102 over the UTRAN 104, asdescribed in greater detail below, for example, with reference to FIG.7.

Turning now to FIG. 2, aspects of a method 200 for selectivelyestablishing an mRAB will be described in detail. It should beunderstood that the operations of the methods disclosed herein are notnecessarily presented in any particular order and that performance ofsome or all of the operations in an alternative order(s) is possible andis contemplated. The operations have been presented in the demonstratedorder for ease of description and illustration. Operations may be added,omitted, and/or performed simultaneously, without departing from thescope of the appended claims.

It also should be understood that the illustrated methods can be endedat any time and need not be performed in their respective entireties.Some or all operations of the methods, and/or substantially equivalentoperations, can be performed by execution of computer-readableinstructions included on a computer-storage media, as defined below. Theterm “computer-readable instructions,” and variants thereof, as used inthe description and claims, is used expansively herein to includeroutines, applications, application modules, program modules, programs,components, data structures, algorithms, and the like. Computer-readableinstructions can be implemented on various system configurations,including single-processor or multiprocessor systems, minicomputers,mainframe computers, personal computers, hand-held computing devices,processor-based, programmable consumer electronics, one or more of thenetwork elements described above with reference to FIG. 1, combinationsthereof, and the like.

Thus, it should be appreciated that the logical operations describedherein are implemented (1) as a sequence of computer-implemented acts orprogram modules running on a computing system and/or (2) asinterconnected machine logic circuits or circuit modules within thecomputing system. The implementation is a matter of choice dependent onthe performance and other requirements of the computing system.Accordingly, the logical operations described herein are referred tovariously as states, operations, structural devices, acts, or modules.These operations, structural devices, acts, and modules may beimplemented in software, in firmware, in special purpose digital logic,and any combination thereof.

For purposes of illustrating and describing the concepts of the presentdisclosure, the methods disclosed herein are described as beingperformed by the MD 102, the RNC 118, and/or the SGSN 126, for example,by execution, respectively, of computer-executable instructionscontained in the mRAB decision application 130, the RNC application 132,and/or the SGSN application 134. It should be understood that theseembodiments are exemplary, and should not be viewed as being limiting inany way. The method 200 is now described with reference to FIG. 2.

The method 200 begins at operation 202, wherein the MD 102 receives adata request. The data request may be a device-initiated,user-initiated, or network-initiated data request, as described ingreater detail above with reference to FIG. 1. For a device-initiated oruser-initiated data request, the receipt of the data request is internalto the MD 102. That is, for example, the MD 102 may receive a datarequest from an application executing on the MD 102. For anetwork-initiated data request, the receipt of the data request is by atransceiver (shown in FIG. 16) of the MD 102.

From operation 202, the method 200 proceeds to operation 204, wherein itis determined if the MD 102 is capable of supporting an mRAB. The mRABdecision application 130 (shown in FIG. 1) may be executed by the MD 102to make this determination.

In some embodiments, the determination made in operation 204 is basedupon whether the MD 102 is currently engaged in a voice communication.If the MD 102 is currently engaged in a voice communication, the MD 102may determine that it is not capable of supporting an mRAB. Otherwise,if the MD 102 is not currently engaged in a voice communication, the MD102 may determine that the MD 102 is capable of supporting an mRAB.Although not shown in the illustrated embodiment, instead of a datarequest, the MD 102 may receive an incoming call. In this case, thedetermination made in operation 204 is based upon whether the MD 102 iscurrently engaged in a data communication.

In other embodiments, the determination made in operation 204 is basedat least partially upon one or more statistics measured by the MD 102and a comparison of the measured statistics to a thresholding algorithm.The one or more statistics measured by the MD 102 may include, but arenot limited to, an uplink transmit (“Tx”) power (i.e., from the MD 102to the node B 116), a downlink received (“Rx”) power (i.e., from thenode B 116 to the MD 102), and/or a number of power-up commands receivedby the MD 102 from the node B 116. In some embodiments, these statisticsare measured by a standalone measuring application that is incommunication with the mRAB decision application 130. In theseembodiments, the measuring application provides the measured statisticsto the mRAB decision application 130 so that the mRAB decisionapplication 130 can make the determination of operation 204. In someembodiments, the measuring application is a diagnostics applicationconfigured to perform diagnostic operations in addition to measuringstatistics. In other embodiments, the statistics are measured directlyby the mRAB decision application 130. In any case, the statistics arecompared to a thresholding algorithm to determine if the MD 102 iscapable of supporting an mRAB.

The thresholding algorithm, in some embodiments, employs a thresholdvalue that, when reached or exceeded, causes the mRAB decisionapplication 130 to determine that the MD 102 is incapable of supportingan mRAB. For example, a threshold may be set to 75% of a maximum uplinkTx power of the MD 102. When the measured uplink Tx power (e.g.,instantaneous or mean over a particular time period) of the MD 102reaches or exceeds a certain percentage (e.g., 75%) of the maximumuplink Tx power, the mRAB decision application 130 determines that it isincapable of supporting an mRAB. The thresholding algorithm mayalternatively consider an available uplink Tx power of the MD 102 which,in the above example, would be 25%. Thresholds may also be set in termsof decibels.

It is contemplated that the thresholding algorithm may employ a learningmodel by which the MD 102 adjusts the threshold value depending uponvarious radio conditions that require more or less power. For example,the MD 102 may require less uplink Tx power to support an mRAB when theMD 102 is located in a rural or suburban environment than when the MD102 is located in an urban environment due to the prevalence ofbuildings, traffic, and other obstacles that imped the propagation ofradio signals in urban environments. The learning model may adjust thethreshold value to require a lower percentage of the maximum uplink Txpower when in certain environments. For example, the MD 102 may, onaverage during a voice session, be using X percent of a total transmitpower Y to maintain the voice session. X may fluctuate higher or lowerdue to various factors such as location type (e.g., urban, suburban, orrural; indoor or outdoor), usage scenario (e.g., time of day, day ofweek, etc.), handset orientation, user mobility, network loading,human-made noise, distance from base station (e.g., the node B 116),signal fading and other signal propagation effects, and the like.Accordingly, the threshold value may be adjusted to compensate for suchfactors. The thresholding algorithm may alternatively be viewed in termsof decibels (“dB”) or dBm instead of percentages.

It is also contemplated that the thresholding algorithm may employ aweighting function that utilizes multiple statistics (e.g., uplink Txpower and downlink Rx power), each weighted by a certain factor tocalculate a weighted result that is used by the thresholding algorithmto determine whether the MD 102 is capable of supporting an mRAB. Othervariations of a thresholding algorithm are described herein below withreference to the other FIGURES.

It should be understood that while the MD 102 may, at times, be capableof supporting an mRAB, doing so would increase the probability of anmRAB failure, potentially resulting in a tear down of the mRAB and adropped call. Accordingly, determining if the MD 102 is capable ofsupporting an mRAB, in some embodiments, is an evaluation of a riskmerit. That is, an evaluation of the risk of a dropped call if an mRABis to be established given the current radio conditions beingexperienced by the MD 102 and the importance of the data prompting theestablishment of the mRAB. In some instances, the risk of a dropped callis tolerable for data that is deemed important to the user, the network100, the mobile network operator providing the network 100, anothermobile network operator, another party, or another entity. For example,from a user perspective, navigation data may be considered important andworth the risk of potentially dropping a voice call. By contrastingexample, an email push may be less crucial than navigation data and, assuch, not worth the risk of potentially dropping a voice call.

In consideration of the determination of operation 204 as a risk meritevaluation, it is contemplated that the MD 102 can store priority datafor various data types and/or various applications. For example, the MD102 may include priority data that instructs the MD 102 to establish anmRAB for certain data types and/or applications based upon theirpriority level even if the determination of operation 204, under normalconditions, yields a result that the MD 102 is incapable of supportingan mRAB. The priority data may be globally set for a data type such thatany application that uses the data type is permitted to access a dataconnection in accordance with a priority level established for the datatype. Alternatively, the priority data may be set on a per applicationbasis such that the priority level of the application controls. Thepriority data may be established by a user, a mobile network operator, athird party, or an entity. In some embodiments, the mobile networkoperator generates and sends a priority data file to the MD 102, so thatthe mobile network operator can control what data types and/orapplications are permitted to request a data connection under certainradio conditions (e.g., under certain threshold values).

From operation 204, the method 200 proceeds to operation 206, whereinthe MD 102 allows or denies establishment of an mRAB based upon thedetermination made in operation 204. In some embodiments, the MD 102notifies the user that a data connection is unavailable if establishmentof an mRAB is denied, as will be described in greater detail below withreference to FIG. 9. In other embodiments, the user is given the optionto override the decision made by the MD 102 to deny establishment of anmRAB, as will be described in greater detail below with reference toFIG. 10. From operation 206, the method 200 proceeds to operation 208.The method 200 ends at operation 208.

Turning now to FIG. 3, aspects of a method 300 for selectivelyestablishing an mRAB based at least partially on an available uplink Txpower of the MD 102 will be described in detail. The method 300 beginsat operation 302, wherein a first RAB (e.g., a vRAB) is establishedbetween the MD 102 and the network 100 to facilitate a voice session.The first RAB may be established in response to a mobile-initiated or amobile-terminated call directed to or received from another deviceoperating within the network 100, another PLMN, the circuit network 110,or the packet network 112. In any case, the first RAB is established andthe voice session between the MD 102 and the other device is carriedout. It is also contemplated that the first RAB may be configured tofacilitate a conference call, wherein the MD 102 is one of three or moredevices participating in the voice session.

From operation 302, the method 300 proceeds to operation 304, whereinuplink Tx power statistics for the MD 102 are collected during the voicesession. In some embodiments, establishment of the voice session promptsthe mRAB decision application 130 to begin, or instruct anotherapplication resident on the MD 102 (e.g., a measuring application) tobegin measuring the uplink Tx power of the MD 102. The Tx powerstatistics may be collected at any periodicity or intermittently, andfor any duration up to and including the entirety of the voice session.

From operation 304, the method 300 proceeds to operation 306, whereinthe MD 102 receives a request to initiate a data session between the MD102 and the network 100. The request received by the MD 102 may be auser-initiated request, a device-initiated request, or anetwork-initiated request in accordance with any of the embodimentsdescribed above.

From operation 306, the method 300 proceeds to operation 308, whereinthe mRAB decision application 130 calculates an available Tx power ofthe MD 102 from the Tx power statistics collected during the operation304. From operation 308, the method 300 proceeds to operation 310,wherein the mRAB decision application 130 determines if a second RAB(e.g., an mRAB) configured to simultaneously support voice and data isto be established based upon the available Tx power of the MD 102calculated in operation 308. From operation 310, the method 300 proceedsto operation 312, wherein the mRAB decision application 130 allows ordenies establishment of the second RAB based upon the determination.From operation 312, the method 300 proceeds to operation 314. The method300 ends at operation 314.

Turning now to FIG. 4, aspects of a method 400 for selectivelyestablishing an mRAB in response to a user-initiated data request willbe described in detail. The method 400 begins and proceeds to operation402, wherein the MD 102 establishes a voice session over a vRAB with thenetwork 100. From operation 402, the method 400 proceeds to operation404, wherein the mRAB decision application 130 collects uplink Tx powerstatistics during the voice session. From operation 404, the methodproceeds to operation 406, wherein the MD 102 receives a user-initiateddata request, such as a user-initiated data request described above withreference to FIG. 1. Alternatively, at operation 406, the MD 102 mayreceive a device-initiated data request. From operation 406, the method400 proceeds to operation 408, wherein the mRAB decision application 130calculates an available Tx power from the Tx power statistics collectedduring the operation 404.

From operation 408, the method 400 proceeds to operation 410, whereinthe mRAB decision application 130 determines if the available Tx powercalculated in operation 408 is sufficient to support an mRAB. Thisdetermination may be based upon a thresholding algorithm, such asdescribed above with reference to FIG. 2. If it is determined atoperation 410 that the available Tx power is sufficient to support anmRAB, the method 400 proceeds to operation 412, wherein the MD 102initiates the establishment of an mRAB, for example, by generating a PDPcontext activation request and sending the PDP context activationrequest to the SGSN 126. The MD 102 and the SGSN 126 carry out theremainder of a PDP context activation procedure and an mRABestablishment procedure. After an mRAB is established, the voice sessioncan be transferred to the mRAB and the vRAB can be torn down.

From operation 412, the method 400 proceeds to operation 414, whereinthe MD 102 executes a data operation associated with the user-initiateddata request. For example, the MD 102 may initiate a data download,request a refresh of data content, initiate a search query, or otherwiseutilize the data connection afforded by the mRAB. From operation 414,the method proceeds to operation 416. The method 400 ends at operation416.

If it is determined at operation 410 that the available Tx power isinsufficient to support an mRAB, the method 400 proceeds to operation418, wherein the mRAB decision application 130 denies the data request.Denial of the data request may be accompanied by a notification to theuser, as described in greater detail below with reference to FIG. 9.Alternatively, denial of the data request may be accompanied by anoverride option that is presented to the user, as described in greaterdetail below with reference to FIG. 10. From operation 418, the method400 proceeds to operation 416. The method 400 ends at operation 416.

Turning now to FIG. 5, aspects of a method 500 for selectivelyestablishing an mRAB in response to a network-initiated data requestwill be described in detail. The method 500 begins and proceeds tooperation 502, wherein the MD 102 establishes a voice session over avRAB with the network 100. From operation 502, the method 500 proceedsto operation 504, wherein the mRAB decision application 130 collectsuplink Tx power statistics during the voice session. From operation 504,the method proceeds to operation 506, wherein the MD 102 receives anetwork-initiated data request, such as a network-initiated data requestdescribed above with reference to FIG. 1. From operation 506, the method500 proceeds to operation 508, wherein the mRAB decision application 130calculates an available Tx power from the Tx power statistics collectedduring operation 504.

From operation 508, the method 500 proceeds to operation 510, whereinthe mRAB decision application 130 determines if the available Tx powercalculated in operation 508 is sufficient to support an mRAB. Thisdetermination may be based upon a thresholding algorithm, such asdescribed above with reference to FIG. 2. If it is determined atoperation 510 that the available Tx power is sufficient to support anmRAB, the method 500 proceeds to operation 512, wherein the network 100initiates the establishment of an mRAB, for example, by generating(e.g., by the SGSN 126) a PDP context activation request and sending thePDP context activation request to the MD 102. The MD 102 and the SGSN126 carry out the remainder of a PDP context activation procedure and anmRAB establishment procedure. After an mRAB is established, the voicesession can be transferred to the mRAB and the vRAB can be torn down.From operation 512, the method 500 proceeds to operation 514, whereinthe MD 102 executes a data operation associated with thenetwork-initiated data request. From operation 514, the method proceedsto operation 516. The method 500 ends at operation 516.

If it is determined at operation 510 that the available Tx power isinsufficient to support an mRAB, the method 500 proceeds to operation518, wherein the mRAB decision application 130 denies the data request.In some embodiments, the MD 102, in response to the mRAB decisionapplication 130 denying the data request, ignores the network-initiateddata request, permitting the data request to be retried and, if the MD102 again determines the available Tx power is insufficient, furtherignore the retry attempt(s) and eventually time out. In theseembodiments, the SGSN 126 may attempt to retransmit the data request tothe MD 102. These attempts may also be ignored, or, after a certainnumber of retries, the MD 102 may respond with a notification that theMD 102 is unable to act on the data request. Denial of the data requestmay be accompanied by a notification to the user, as described ingreater detail below with reference to FIG. 9. Alternatively, denial ofthe data request may be accompanied by an override option that ispresented to the user, as described in greater detail below withreference to FIG. 10. From operation 518, the method 500 proceeds tooperation 516. The method 500 ends at operation 516.

Turning now to FIG. 6, aspects of another method 600 for selectivelyestablishing an mRAB will be described in detail. The method 600 beginsand proceeds to operation 602, wherein the MD 102 collects uplink Txpower statistics, according to the methods described above. Fromoperation 602, the method 600 proceeds to operation 604, wherein the MD102 exposes the uplink Tx power statistics collected in operation 602 tothe mRAB decision application 130. The Tx power statistics may becollected at any periodicity or intermittently, and for any duration. Insome embodiments, the mRAB decision application 130 collects the uplinkTx power statistics and, as such, operation 604 is omitted. Otherwise,if another application (e.g., a measuring application) collects theuplink Tx power statistics, that application exposes the uplink Tx powerstatistics to the mRAB decision application 130 at operation 604.

From operation 604, the method proceeds to operation 606, wherein themRAB decision application 130 calculates a mean (i.e., an average) Txpower from the uplink Tx power statistics. The mean Tx power may becalculated using any number of instantaneous uplink Tx power samplescollected during operation 602. Moreover, the mean Tx power may becalculated using at least portion of the uplink Tx power samplescollected during operation 602.

From operation 606, the method 600 proceeds to operation 608, whereinthe mRAB decision application 130 calculates a standard deviation usingthe mean Tx power calculated in operation 606 and the uplink Tx powerstatistics. From operation 608, the method 600 proceeds to operation610, wherein the mRAB decision application 130 calculates the mean Txpower plus one standard deviation.

From operation 610, the method 600 proceeds to operation 612, wherein itis determined if the result of operation 610 (i.e., the calculated meanTx power plus one standard deviation) meets or exceeds a thresholdvalue. For example, the threshold value may be set to a certainpercentage of a maximum uplink Tx power of the MD 102. If the resultdoes not meet or exceed the threshold value, there is sufficient uplinkTx power to support an mRAB. Accordingly, the method 600 proceeds fromoperation 612 to operation 614, wherein the mRAB decision application130 allows establishment of an mRAB. From operation 614, the method 600proceeds to operation 616. The method 600 ends at operation 616. If theresult meets or exceeds the threshold value, the method 600 proceeds tooperation 618, wherein the mRAB decision application 130 deniesestablishment of an mRAB. From operation 618, the method 600 proceeds tooperation 616, wherein the method 600 ends.

It is contemplated that the threshold value can be generated using alearning model by which the MD 102 adjusts the threshold value dependingupon various radio conditions that require more or less power. Forexample, the MD 102 may require less uplink Tx power to support an mRABwhen the MD 102 is located in a rural or suburban environment than whenthe MD 102 is located in an urban environment due to the prevalence ofbuildings, traffic, and other obstacles that imped the propagation ofradio signals in urban environments. Accordingly, the learning model mayadjust the threshold value to require a lower percentage of the maximumuplink Tx power when in certain environments. This may be based at leastpartially upon location data received from a location component (shownin FIG. 16) of the MD 102 and/or historical power statistics collectedover time that may or may not be correlated with location data. It isalso contemplated that the threshold value can be generated using aweighting function that utilizes multiple statistics (e.g., uplink Txpower and downlink Rx power), each weighted by a certain factor tocalculate a weighted result that is used to determine whether the MD 102is capable of supporting an mRAB.

Turning now to FIG. 7, aspects of a method 700 for operating the SGSN126 will be described in detail. The method 700 begins and proceeds tooperation 702, wherein the SGSN 126 receives data directed to the MD 102from the GGSN 128. From operation 702, the method 700 proceeds tooperation 704, wherein the SGSN 126 sends a data request (e.g., in theform of a PDP context activation request, other message during a PDPcontext activation procedure, or a message associated with theestablishment of a RAB) to the RNC 118.

From operation 704, the method 700 proceeds to operation 706, whereinthe SGSN 126 receives instructions from the RNC 118 to delay delivery ofdata associated with the data request to the MD 102. In someembodiments, the instructions received from the RNC 118 are based upon anotification received by the RNC 118 from the MD 102 indicating thatsufficient uplink Tx power is currently not available to establish anmRAB. The notification may be implicit such as by one or more previousattempts to contact the MD 102 to establish a data connection beingignored, or explicit such as by a message received at the RNC 118 fromthe MD 102. In some embodiments, the RNC 118 determines that the MD 102is currently not available to establish an mRAB. This may be determined,for example, using a downlink Tx power of the node B 116 to the MD 102for a current voice call as an estimate of the uplink Tx power of the MD102.

From operation 706, the method 700 proceeds to operation 708, whereinthe SGSN 126 checks the data type of the data received from the GGSN128. In some embodiments, the SGSN application 134 (shown in FIG. 1)stores a retry interval and a number of retry attempts for various datatypes. In some embodiments, the retry intervals and/or the number ofretry attempts are set by a mobile network operator, an operator of theSGSN 126, a user of the MD 102, or another party. In some embodiments,the retry intervals and/or the number of retry attempts are setaccording to a priority scheme, wherein certain data types have a higherpriority than others. In this manner, a mobile network operator, forexample, can prioritize which type(s) of data is sent to a target devicewhen the target device is engaged in a voice call.

From operation 708, the method 700 proceeds to operation 710, whereinthe SGSN 126 determines a retry interval based upon the data typedetermined in operation 708. Operation 710 may be a look-up operation,wherein the SGSN application 134 looks up the retry interval and/or thenumber of retry attempts associated with the determined data type in atable stored in the SGSN 126. From operation 710, the method 700proceeds to operation 712, wherein the SGSN 126 retries transmission ofthe data request to the RNC 118 based upon the retry interval determinedin operation 710. The retry interval can be any interval.

From operation 712, the method 700 proceeds to operation 714, wherein itis determined if a retry attempt was successful. If a retry attempt wassuccessful, the method 700 proceeds from operation 714 to operation 716,wherein the SGSN 126 sends the data to the RNC 118 for delivery to theMD 102 via the node B 116. From operation 716, the method 700 proceedsto operation 718. The method 700 ends at operation 718. If a retryattempt was not successful, the method 700 proceeds to operation 720,wherein it is determined if the number of retry attempts has beenexhausted. If the number of retry attempts has not been exhausted, themethod 700 proceeds to operation 712, wherein the SGSN 126 again retriestransmission of the data based upon the retry interval. If the number ofretry attempts has been exhausted, however, the method 700 proceeds tooperation 722, wherein the SGSN 126 notifies the GGSN 128 of the failedretry attempts. The GGSN may then notify the server 114 or other datasource that the data cannot be transmitted to the MD 102. From operation722, the method 700 proceeds to operation 718, wherein the method 700ends.

Turning now to FIG. 8, aspects of a method 800 for operating the RNC 118will be described in detail. The method 800 begins and proceeds tooperation 802, wherein the RNC 118 receives a data request from the SGSN126. From operation 802, the method 800 proceeds to operation 804,wherein the RNC 118 determines that the available uplink Tx power of theMD 102 is insufficient to support an mRAB. In some embodiments, thisdetermination is made based upon information received from the MD 102.The information may be implicit such as by one or more previous attemptsto contact the MD 102 to establish a data connection being ignored, orexplicit such as by a message received from the MD 102 in response to aprevious attempt (e.g., a denied PDP context activation request). Itshould be understood that the previous attempts may be associated withthe data request received in operation 802 or another data requestreceived within a predetermined time period of the RNC 118 receiving thedata request.

From operation 804, the method 800 proceeds to operation 806, whereinthe RNC 118 holds the data request and prompts the SGSN 126 to bufferdata associated with the data request. From operation 806, the method800 proceeds to operation 808, wherein the RNC 118 retries transmissionof the data request to the MD 102 based upon a retry interval. The retryinterval can be set in the RNC application 132 at any interval. Forexample, if the average voice call experienced by the RNC 118 is knownto be between 100 and 120 seconds, the RNC application 132 can be setwith a retry interval of 120 seconds which would, on average, besuccessful on a second retry attempt. The retry interval may be set by amobile network operator, an operator of the RNC 118, a user of the MD102, or another party.

From operation 808, the method 800 proceeds to operation 810, wherein itis determined if a retry attempt was successful. If a retry attempt wassuccessful, the method 800 proceeds from operation 810 to operation 812,wherein the RNC 118 requests and receives the buffered data from theSGSN 126. From operation 812, the method 800 proceeds to operation 814,wherein the RNC 118 sends the data to the MD 102 via the node B 116.From operation 814, the method 800 proceeds to operation 816. The method800 ends at operation 816. If a retry attempt was not successful, themethod 800 proceeds to operation 818, wherein it is determined if anumber of retry attempts has been exhausted. If the number of retryattempts has not been exhausted, the method 800 proceeds to operation808, wherein the RNC 118 again retries transmission of the data requestbased upon the retry interval. If the number of retry attempts has beenexhausted, however, the method 800 proceeds to operation 820, whereinthe RNC 118 notifies the SGSN 126 of the failed retry attempts. The SGSN126 may then notify the GGSN 128 that the data cannot be transmitted tothe MD 102. The GGSN 128 may, in turn, notify the server 114 or otherdata source of the same. From operation 820, the method 800 proceeds tooperation 816, wherein the method 800 ends.

Turning now to FIG. 9, aspects of a method 900 for notifying a user thata data connection is currently unavailable will be described in detail.The method 900 begins and proceeds to operation 902, wherein it isdetermined that the MD 102 is incapable of supporting an mRAB. Thisdetermination may be made based upon any of the applicable methodsdisclosed herein above.

From operation 902, the method 900 proceeds to operation 904, whereinthe MD 102 notifies the user that a data connection is currentlyunavailable. In some embodiments, the MD 102 notifies the user usingvisible, audible, and/or tactile notification mechanisms. In particular,the MD 102 may use text, graphics, videos, sounds, music, vibrations, orcombinations thereof to notify the user that a data connection iscurrently unavailable. It is contemplated that the mechanism by whichsuch notifications are presented to the user be configurable by theuser, a mobile network operator, a third party (e.g., a devicemanufacturer or device software developer/distributor), or somecombination thereof. Moreover, the notification can be triggered at theoperating system or application level. In some embodiments, an operatingsystem or an application receives a trigger to present the notificationvia the mRAB decision application 130. From operation 904, the method900 proceeds to operation 906. The method 900 ends at operation 906.

Turning now to FIG. 10, aspects of a method 1000 for providing a useroverride option will be described in detail. The method 1000 begins andproceeds to operation 1002, wherein it is determined that the MD 102 isincapable of supporting an mRAB. From operation 1002, the method 1000proceeds to operation 1004, wherein the MD 102 prompts the user toselect a continuation option. In the illustrated embodiment,continuation options include an option to continue with a dataconnection and an option not to continue with a data connection. Inother embodiments, the continuation options include selectable optionsfor various uplink and/or downlink data rates, one or more of which mayhave different power requirements to support. In these embodiments, themRAB decision application 130 may be configured to suggest a data ratebased upon the available uplink Tx power of the MD 102. In someembodiments, a default option (e.g., continue, do not continue, orselect a slower data rate that requires less power) is set.

From operation 1004, the method 1000 proceeds to operation 1006, whereinthe MD 102 receives a selection of a continuation option. From operation1006, the method 1000 proceeds to operation 1008, wherein it isdetermined if the selected continuation option is to continue with theestablishment of an mRAB. If the selected continuation option is not tocontinue, the method 1000 proceeds from operation 1008 to operation1010, wherein the MD 102 notifies the user that a data connection iscurrently unavailable. The notification used in operation 1010 may besimilar to the notification described above with reference to FIG. 9.From operation 1010, the method 1000 proceeds to operation 1012. Themethod 1000 ends at operation 1012.

If the selected continuation option is to continue, the method 1000proceeds from operation 1008 to operation 1014, wherein the MD 102presents a warning to the user indicating that their call may be droppedshould they choose to continue with a data connection. In theillustrated embodiment, at operation 1014, the MD 102 also prompts theuser to confirm their selection to continue after presentation of thewarning. From operation 1014, the method 1000 proceeds to operation1016, wherein it is determined if the user has confirmed their selectionto continue. If the user does not confirm their selection to continue,the method 1000 proceeds from operation 1016 to operation 1010, whereinthe MD 102 notifies the user that a data connection is currentlyunavailable. From operation 1010, the method 1000 proceeds to operation1012, wherein the method 1000 ends. If, at operation 1016, the userconfirms their selection to continue, the method 1000 proceeds fromoperation 1016 to operation 1018, wherein a data connection isestablished over an mRAB. Alternatively, the warning presented inoperation 1014 may be presented without prompting the user forconfirmation and the method 1000 proceeds automatically from operation1014 to operation 1018. In any case, from operation 1018, the method1000 proceeds to operation 1012, wherein the method 1000 ends.

Turning now to FIG. 11, aspects of a method 1100 for prioritizing voicecalls over data communications based upon a selection of a voicepriority option will be described. The method 1100 begins and proceedsto operation 1102, wherein a voice prioritized option is displayed. Insome embodiments, the voice prioritized option is displayed as a singleselectable option. For example, the voice prioritized option may bedisplayed along with a check box, a radio button, or some other GUIelement, the selection/de-selection of which visually distinguishesbetween a selected state and a non-selected state of the voiceprioritized option. In the illustrated embodiment, the voice prioritizedoption is displayed in context of one or more other options, such as avoice only (i.e., no data) option and/or a voice and data (i.e., normaloperation) option.

In some embodiments, the voice prioritized option is displayed prior toa voice call being established, during establishment of a voice call,during a voice call, and/or after a voice call. In some embodiments, thevoice priority option is provided as part of the MD application 130, aspart of a dialer application of the MD 102, as part of an operatingsystem (best shown in FIG. 16) of the MD 102, and/or as part of asoftware widget. Exemplary GUIs including a voice priority option aredescribed below with reference to FIGS. 12A-12C.

From operation 1102, the method 1100 proceeds to operation 1104, whereina selection of one of the options is received. It should be understoodthat the selection of one of the options may be effected through aninput interface of the MD 102, such as the input interface describedbelow with reference to FIG. 16. Other input methods such as voicerecognition or remote control are contemplated.

At operation 1106, it is determined if the voice prioritized option hasbeen selected. If the voice prioritized option has been selected, themethod 1100 proceeds to operation 1108, wherein data access isconditionally denied in accordance with settings established for thevoice prioritized option. In some embodiments, the selection of thevoice prioritized option enables the MD 102 to perform one of the othermethods, such as the methods described herein above with reference toFIGS. 2-6. In some embodiments, data access is denied when a poor radiofrequency condition is experienced by the MD 102. In some embodiments,data access is denied when a poor RF condition is experienced by the MD102, unless a user initiates a data session. In some embodiments, dataaccess is permitted only for a specified one or more applications.

A poor RF condition may exist if the uplink Tx power of the MD 102exceeds a particular threshold such as a maximum uplink Tx power, asdescribed in greater detail above. A poor RF condition may be determinedto exist based at least in part upon a received signal code power(“RSCP”), a ratio of the received energy and the interference level(i.e., Ec/Io), a carrier-to-noise ratio (i.e., Ec/N0), and/or thereceived signal strength indicator (“RSSI”). The threshold values forwhat constitutes a poor RF condition may be determined by the serviceprovider or another entity, such as the user of the MD 102 or a remoteentity. A poor RF condition may be determined to exist based at least inpart upon other metrics.

From operation 1108, the method 1100 proceeds to operation 1110. Themethod 1100 ends at operation 1110.

If, at operation 1106, it is determined that the voice prioritizedoption has not been selected, the method 1100 proceeds to operation1112. At operation 1112, it is determined if a voice only option hasbeen selected. If a voice only option has been selected, the method 1100proceeds to operation 1114, wherein only voice calls are allowed (i.e.,no data is allowed under any condition). The method 1100 then proceedsto operation 1110, wherein the method 1100 ends.

If, at operation 1112, it is determined that the voice only option hasnot been selected, the method 1100 proceeds to operation 1116, whereinvoice and data is allowed. In other words, the MD 102 is allowed toperform operations that require voice and/or data access in accordancewith normal operations. The method 1100 then proceeds to operation 1110,wherein the method 1100 ends.

Turning now to FIGS. 12A-12C, various exemplary GUIs illustratingvarious means by which a voice priority option can be selected will bedescribed. With particular reference to FIG. 12A, a network overview GUI1200 is illustrated. The network overview GUI 1200 includes a status bar1202, a navigation bar 1204, and a main body 1206.

The illustrated status bar 1202 includes a signal strength indicator, acarrier/service provider identifier (e.g., “AT&T”), a service typeidentifier (e.g., “3G”), a time, and a battery level indicator.Alternative and/or additional indicators and/or identifiers arecontemplated. For example, certain operations executed by the MD 102 maycause a particular icon or other visual representation to be presentedin the status bar 1202 to indicate a status of the operation, such asactive, not active, or the like. In some embodiments, an icon or othervisual representation (not shown) representing a selection of a voiceprioritized option, a voice only option, or a voice and data isdisplayed in the status bar 1202.

The illustrated navigation bar 1204 includes a previous button 1208 thatis used to navigate to a previous screen which, in the illustratedembodiment, is a “general” screen. The navigation bar 1204 also includesa title (not labeled) of “Network” identifying that settings presentedin the main body 1206 are relevant to network details. Alternativeand/or additional buttons may be displayed in the navigation bar 1204.

The illustrated main body 1206 includes a maximum data coverage selector1210, a maximum voice coverage selector 1212, and voice only selector1214, each of which is associated with a toggle button 1216, 1218, 1220,respectively. The toggle buttons 1216, 1218, 1220 allow a user to togglethe features provided by the selectors 1210, 1212, 1214. In particular,toggling the toggle button 1216 of the maximum data coverage selector1210 to “ON”, as in the illustrated embodiment, allows simultaneousvoice and data communications in accordance with normal operation;toggling the toggle button 1218 of the maximum voice coverage selector1212 to “ON” prioritizes voice over data; and toggling the toggle button1220 to “ON” activates a voice only such that data is never allowed. Itis contemplated that not all of the selectors 1210, 1212, 1214 may bepresented. For example, the maximum voice coverage selector 1212 may bethe only option available such that the user may prioritize voice ornot. Moreover, alternative labeling is contemplated as is needed to bestconvey the outcome of activating a particular selector.

In some embodiments, selection of the maximum voice coverage selector1212 causes the automatic shutdown of data access when certain RFconditions are experienced by the MD 102. For example, if the MD 102experiences an established low RSSI or an established high Ec/NO, dataaccess may be shutdown. To summarize without limitation, the MDapplication 130 may turn off data access during voice calls and per RFthresholds when the maximum voice coverage selector 1212 is selected.Moreover, the MD application 130 may turn on data access when themaximum voice selector 1212 is selected and if the MD 102 experiences RFconditions that pass established thresholds. In some embodiments, thethreshold is passed in addition to a certain hysteresis.

The illustrated main body 1206 also includes a settings menu option1222. Selection of the settings menu option 1222 navigates to a networksettings GUI 1300 that is illustrated and described below with referenceto FIG. 13.

The options for voice and data, voice prioritized, and/or voice only maybe provided in alternative forms, such as via a software widget. Twoexemplary software widgets are illustrated in FIGS. 12B and 12C. Inparticular, FIG. 12B illustrates a simple software widget 1224 includingradio buttons 1226, 1228, 1230, the selection of which activates,respectively, a voice and data option, a voice prioritized option, or avoice only option. The simple software widget 1224 may be displayed, forexample, on a home screen of a mobile device running an operating systemthat supports software widgets (e.g., ANDROID OS from GOOGLE INC.) or,alternatively, a software application that enables support for softwarewidgets for an operating system that does not natively support softwarewidgets.

FIG. 12C illustrates an advanced software widget 1232 including a voiceand data button 1234, a voice prioritized button 1236, and a voice onlybutton 1238. Each of the buttons 1234, 1236, 1238 is associated with anindicator bar 1240, 1242, 1244, respectively. Selection of one of thebuttons 1234, 1236, 1238 causes modification of the correspondingindicator bar 1240, 1242, 1244 to convey the selection. For example, theselected indicator bar (the indicator bar 1242 in the illustratedembodiment) may change color, change brightness, change contrast, changefrom a static state to an animated state, or otherwise be visuallymodified so as to appear different to user from a non-selectedappearance. The advanced software widget 1232 also includes an extrasbutton 1246, the selection of which may provide a user access toadditional information such as settings.

It should be understood that the GUIs 1200, 1224, 1232 may not includeall of the elements shown in FIGS. 12A-12C, may include other elementsthat are not explicitly shown in FIG. 12A-12C, or may utilize one ormore elements that are completely different than those shown in FIGS.12A-12C. It also should be understood that the design of the GUIs may beconsistent with a GUI theme of a particular operating system orapplication, may be an existing proprietary GUI design, or may be a newGUI design. Moreover, the features provided by the GUIs 1200, 1224, 1232may be implemented in other applications, such as in a dialerapplication.

Turning now to FIG. 13, a network settings GUI 1300 illustrating voicepriority settings will be described. The illustrated network settingsGUI 1300 includes a status bar 1302, a navigation bar 1304, and a mainbody 1306. It should be understood that access to the following settingsmay be protected by a password and/or some other authenticationmechanism such that only authorized individuals can access the settings.

The illustrated status bar 1302 includes a signal strength indicator, acarrier/service provider identifier (e.g., “AT&T”), a service typeidentifier (e.g., “3G”), a time, and a battery level indicator.Alternative and/or additional indicator and/or identifier arecontemplated. For example, certain operations executed by the MD 102 maycause a particular icon or other visual representation to be presentedin the status bar 1302 to indicate a status of the operation, such asactive, not active, or the like. In some embodiments, an icon or othervisual representation (not shown) representing a selection of a voiceprioritized option, a voice only option, or a voice and data isdisplayed in the status bar 1302.

The illustrated navigation bar 1304 includes a previous button 1308 thatis used to navigate to a previous screen which, in the illustratedembodiment, is a network screen, such as the network overview GUI 1200illustrated in FIG. 12A. The navigation bar 1304 also includes a title(not labeled) of “Settings”. Alternative and/or additional buttons maybe displayed in the navigation bar 1304.

The upper portion of the illustrated main body 1306 includes an averagetime input box 1310, a threshold input box 1312, and a hysteresis inputbox 1314. In some embodiments, one or more of the input boxes 1310,1312, 1314 are populated with values at the discretion of a user, suchas a tester. In some embodiments, one or more of the input boxes 1310,1312, 1314 are populated remotely. For example, a server, such as one ofthe servers 114, may be configured to send values to the MD 102 forinput into an appropriate one or more of the input boxes 1310, 1312,1314, such as described in greater detail below with reference to FIG.14. Alternative and/or additional input boxes are contemplatedincluding, but not limited to, an input box for Ec/Io.

The illustrated average time input box 1310 includes an average timevalue of “10” in seconds. This identifies the average time in seconds ofa measurement sample or time between measurement samples. The averagetime may be more or less based upon the needs of a particularimplementation. Moreover, the average time may be valued in terms of adifferent time metric, such as, but not limited to, milliseconds orminutes.

The illustrated threshold input box 1312 includes a threshold powervalue of “−96” in dBm. In some embodiments, this threshold value is thesame as the threshold value utilized in the method 600 illustrated anddescribed above with reference to FIG. 6 and as described elsewhereherein. The threshold power value may be more or less based upon theneeds of a particular implementation. Although the threshold power valueis expressed in terms of dBm, other units are contemplated.

The illustrated hysteresis input box 1314 includes a hysteresis value of“5” in dB. In some embodiments, the hysteresis value is used todetermine when to turn data back on. The hysteresis value may be more orless based upon the needs of a particular implementation. Although thehysteresis value is expressed in terms of dB, other units arecontemplated.

The lower portion of the illustrated main body 1306 includes a defaultsetting after a call. The illustrated default setting options include amaximize data coverage option 1316, a maximize voice coverage option1318, a voice only option 1320, and a none option 1322, each of which isassociated with a radio button for selection. These options areconsistent with the same options described above with reference to FIG.12A, but are designated as default options after a call.

The lower portion of the illustrated main body 1306 also includes uploadoptions. The illustrated upload options include an upload dataimmediately option 1324 and an upload data at X time option. The uploaddata immediately option 1324, when selected via the illustrated radiobutton, uploads any measurement data immediately when it is available.Alternatively, when the upload data at X time option is selected,measurement data is sent at X time. For example, a service provider maydesire to configure this setting such that measurement data is sent atmidnight or at some other time chosen to minimize impact, such as at ahistorically low-data-use time. It is contemplated that the X time mayalternatively represent a time range.

The illustrated main body 1306 also includes a control settings remotelyoption 1328 and a save button 1330. In the illustrated embodiment, acheck box associated with the control settings remotely option 1328 ischecked, indicating that the settings described above are controlled bya remote entity, such as one of the servers 114. In some embodiments,the aforementioned settings are grayed-out, blacked-out, non-functional,non-viewable, or otherwise not editable by a user if the controlsettings remotely option 1328 is checked. In some embodiments, a usermay override the control settings remotely option 1328.

Turning now to FIG. 14, aspects of a method 1400 for remotelyconfiguring voice priority settings will be described. The method 1400begins and proceeds to operation 1402, wherein one or more values forone or more voice priority settings are received at the MD 102 from aserver, such as one of the servers 114. From operation 1402, the method1400 proceeds to operation 1404, wherein the voice priority value(s) arestored.

In some embodiments, the values are saved in one or more of the inputboxes 1310, 1312, 1314 (shown in FIG. 13) and/or one or more other inputboxes (not shown). For example, the MD 102 may receive a value for anaverage time, a power threshold, a hysteresis, an Ec/Io, and/or othersettings or statistics described herein. In some embodiments, the one ormore values for the one or more voice priority settings received fromthe server toggle the maximum data coverage, the maximum voice coverage,or the voice only options, or other options described herein. In thismanner, a service provider can remotely control which mobile devicesoperating on their network are able to receive data. This can be used,for example, for testing (e.g., the mobile devices are being used bytesters) and/or for data usage throttling to prevent certain users fromexcess usage of data service for the benefit of the user (e.g., toprevent data overage charges) and/or the service provider (e.g., toprevent abuse of unlimited data plans).

From operation 1404, the method 1400 proceeds to operation 1406, whereina voice call is established. The method 1400 then proceeds to operation1408, wherein data access is allowed or denied based upon the voicepriority setting(s). This may be consistent, for example, with the othermethods described herein. From operation 1408, the method 1400 proceedsto operation 1410, wherein the method 1400 ends.

Turning now to FIG. 15, aspects of a method 1500 for reporting measuredstatistics to a remote server, such as one of the servers 114, will bedescribed. In some embodiments, the remote server is the same as theserver described above in FIG. 14.

The method 1500 begins and proceeds to operation 1502, wherein a voicecall is established. From operation 1502, the method 1500 proceeds tooperation 1504, wherein the MD 102 initiates a measurement application.In some embodiments, operation 1502 and operation 1504 are performedsimultaneously. In some embodiments, operation 1502 and operation 1504are performed sequentially. The measurement application may also beinitiated prior to a voice call being established. For example, themeasurement application may be running in the background and “wake-up”upon a voice call being initiated such that various measurements can beobtained. The measurement application may be configured as describedabove.

From operation 1504, the method 1500 proceeds to operation 1506, whereinthe measurement application measures one or more statistics. Table 1,illustrated below, includes various exemplary statistics the measuringapplication can collect in accordance with the method 1500. For example,some of the statistics are measured during the call while others aremeasured after the call. It should be understood that other statisticsmay be added as needed for a particular implementation.

From operation 1506, the method proceeds to operation 1508, wherein thecall is torn down. From operation 1508, the method proceeds to operation1510, wherein the measured statistics are reported. As noted above, someof the statistics may be measured after the call and, as such, a secondmeasurement operation may be performed after the call is torn down atoperation 1508. In the illustrated embodiment, the measured statisticsare reported to the server after the call is torn down. Alternatively oradditionally, one or more of the measured statistics may be reportedduring the call. The method 1500 ends at operation 1512.

TABLE 1 Exemplary statistics for measurement. Statistic Record ID formeasurement session Phone number for mobile device Time stamp formeasurement session Counter in seconds user in setting 1 (e.g., maximumdata coverage) Counter in seconds user in setting 2 (e.g., maximum voicecoverage) Counter in seconds user in setting 1 (e.g., voice only)Counter in seconds user having data session in setting 1 Counter inseconds user having data session in setting 2 Average RSSI for setting 1Average RSSI for setting 2 when data is enabled Average RSSI for setting2 when data is disabled Average RSSI for setting 3 Call terminationstatus (e.g., user-terminated or dropped call) Latitude of mobile deviceat end of call Longitude of mobile device at end of call List of allopen applications List of all applications on mobile device thatgenerated data during call Last application setting when call hang upoccurred and before application reset back to voice prioritized Batterylevel at beginning of the call Battery level at end of the call LastRSSI Data usage during setting 1 Data usage during setting 2 Networktype at end of the call WIFI used during the call? Cell ID at end of thecall Application version number WIFI active at end of call Mobile devicemake and model

Turning now to FIG. 16, an exemplary mobile communications device, suchas the MD 102, and the components thereof is illustrated, according toan exemplary embodiment. Although connections are not shown between thecomponents illustrated in FIG. 16, the components can interact with eachother to carry out device functions. In some embodiments, for example,the components are arranged so as to communicate via one or more busses(not shown). It should be understood that FIG. 16 and the followingdescription are intended to provide a general understanding of asuitable environment in which various aspects of embodiments can beimplemented.

As illustrated in FIG. 16, the MD 102 includes a display 1602 fordisplaying data including, but not limited to, graphical user interface(“GUI”) elements, text, images, video, virtual keypads and/or keyboards,messaging data, notification messages, metadata, internet content,device status, time, date, calendar data, device preferences, map andlocation data, profile selection (e.g., loud or silent mode), and thelike. The MD 1602 also includes a processor 1604 for processing dataand/or executing computer-executable instructions of one or moreapplications 1606 stored in a memory 1608. In some embodiments, theapplications 1606 include a user interface (“UI”) application 1610. TheUI application 1610 interfaces with a client application 1612 (e.g., anoperating system) to facilitate user interaction with devicefunctionality and data. In some embodiments, the client application 1612is one of SYMBIAN OS from SYMBIAN LIMITED, WINDOWS MOBILE OS fromMICROSOFT CORPORATION, WINDOWS PHONE OS from MICROSOFT CORPORATION, PALMWEBOS from HEWLETT PACKARD CORPORATION, BLACKBERRY OS from RESEARCH INMOTION LIMITED, IOS from APPLE CORPORATION, and ANDROID OS from GOOGLEINC. These operating systems are merely exemplary of the operatingsystems that may be used in accordance with the embodiments disclosedherein.

The UI application 1610 aids a user in activating service over-the-air,if applicable, entering message content, viewing received messages,answering/initiating calls, entering/deleting data, entering and settinguser IDs and passwords for device access, configuring settings,manipulating address book content and/or settings, multimodeinteraction, interacting with other applications 1614, and otherwisefacilitating user interaction with the client application 1612 and/orthe other applications 1614.

In some embodiments, the other applications 1614 include, for example,visual voicemail applications, messaging applications, presenceapplications, text-to-speech and speech-to-text applications, add-ons,plug-ins, email applications, music applications, video applications,camera applications, location-based service applications, powerconservation applications, game applications, productivity applications,entertainment applications, enterprise applications, combinationsthereof, and the like. The other applications 1614 also include the mRABdecision application 130. The mRAB decision application 130 isconfigured as described above with reference to the other FIGURES. Theapplications 1606 are stored in the memory 1608 and/or in a firmware1616, and are executed by the processor 1604. The firmware 1616 may alsostore code for execution during device power up and power downoperations.

The MD 102 also includes an input/output (“I/O”) interface 1618 for theinput/output of data such as location information, presence statusinformation, user IDs, passwords, and application initiation (start-up)requests. In some embodiments, the I/O interface 1618 is a hardwireconnection such as a universal serial bus (“USB”), mini-USB, micro-USB,audio jack, PS2, IEEE 1394, serial, parallel, Ethernet (RJ48) port, RJ11port, proprietary port, combinations thereof, or the like. In someembodiments, the MD 102 is configured to synchronize with another device(e.g., a computer) to transfer content stored to/from the MD 102. Insome embodiments, the MD 102 is configured to receive updates to one ormore of the applications 1606 via the I/O interface 1618. In someembodiments, the I/O interface 1618 accepts I/O devices such askeyboards, keypads, mice, interface tethers, printers, plotters,external storage, touch/multi-touch screens, touch pads, trackballs,joysticks, microphones, remote control devices, displays, projectors,medical equipment (e.g., stethoscopes, heart monitors, and other healthmetric monitors), modems, routers, external power sources, dockingstations, combinations thereof, and the like. It should be appreciatedthat the I/O interface 1618 may be used for communications between theMD 102 and a network device or local device instead of, or in additionto, a communications component 1620.

The communications component 1620 interfaces with the processor 1604 tofacilitate wireless communications with one or more networks such as thenetwork 100 (shown in FIG. 1) and/or other networks. In someembodiments, other networks include another PLMN while the MD 102 isroaming outside of the network 100. In other embodiments, other networksinclude networks that utilize non-cellular wireless technologies such asWIFI or WIMAX. In some embodiments, the communications component 1620includes a multimode communications subsystem for facilitatingcommunications via the network 100 and one or more other networks.

The communications component 1620, in some embodiments, includes one ormore transceivers each configured to communicate over the same or adifferent wireless technology standard. For example, the transceivers ofthe communications component 1620 may be configured to communicate usingGlobal System for Mobile communications (“GSM”), CDMAONE, CDMA2000, LongTerm Evolution (“LTE”), and various other 2G, 2.5G, 3G, 4G, and greatergeneration technology standards. Moreover, the communications component1620 may facilitate communications over various channel access methods(which may or may not be used by the aforementioned standards)including, but not limited to, Time Division Multiple Access (“TDMA”),Frequency Division Multiple Access (“FDMA”), W-CDMA, OrthogonalFrequency Division Multiplexing (“OFDM”), Space Division Multiple Access(“SDMA”), and the like. In addition, the communications component 1620may facilitate data communications using General Packet Radio Service(“GPRS”), Enhanced Data rates for Global Evolution (“EDGE”), theHigh-Speed Packet Access (“HSPA”) protocol family including High-SpeedDownlink Packet Access (“HSDPA”), Enhanced Uplink (“EUL”) or otherwisetermed High-Speed Uplink Packet Access (“HSUPA”), Evolved HSPA(“HSPA+”), and various other current and future wireless data accessstandards.

In the illustrated embodiment, the communications component 1620includes a first cellular transceiver 1622 that operates in one mode(e.g., GSM), and an N^(th) cellular transceiver 1624 operates in adifferent mode (e.g., UMTS). While only two cellular transceivers 1622,1624 are illustrated, it should be appreciated that more than twotransceivers can be included in the communications component 1620.

The illustrated communications component 1620 also includes analternative communications transceiver 1626 for use by othercommunications technologies including WIFI, WIMAX, BLUETOOTH, infrared,infrared data association (“IRDA”), near field communications (“NFC”),other RF, combinations thereof, and the like. In some embodiments, thecommunications component 1620 also facilitates reception fromterrestrial radio networks, digital satellite radio networks,internet-based radio service networks, combinations thereof, and thelike.

The communications component 1620 processes data from a network such asan internet, an intranet, a home broadband network, a WIFI hotspot, andthe like, via an internet service provider (“ISP”), digital subscriberlink (“DSL”) provider, or broadband provider.

Audio capabilities for the MD 102 may be provided by an audio I/Ocomponent 1628 that includes a speaker for the output of audio signalsand a microphone to collect audio signals.

The illustrated MD 102 also includes a USIM system 1630 that includes aSIM slot interface 1632 for accommodating a USIM card. In someembodiments, the USIM system 1630 is configured to accept insertion ofother SIM cards for access to other network types such as GSM. In otherembodiments, the USIM system 1630 is configured to accept multiple SIMcards. In still other embodiments, the USIM system 1630 is configured toaccept a universal integrated circuit card (“UICC”) with one or more SIMapplications stored thereupon.

The MD 102 may also include an image capture and processing system 1634(“image system”). Photos may be obtained via an associated image capturesubsystem of the image system 1634, for example, a camera. The MD 102may also include a video system 1636 for capturing, processing,recording, and/or modifying video content. Photos and videos obtainedusing the image system 1634 and the video system 1636, respectively, maybe added as message content to a multimedia messaging service (“MMS”)message and sent to another mobile device.

The illustrated MD 102 also includes a location component 1638 forsending and/or receiving signals such as global positioning system(“GPS”) data, assisted GPS (“A-GPS”) data, WIFI/WIMAX and/or cellularnetwork triangulation data, combinations thereof, and the like, fordetermining a location of the MD 102. The location component 1638 maycommunicate with the communications component 1620 to retrievetriangulation data for determining a location of the MD 102. In someembodiments, the location component 1638 interfaces with cellularnetwork nodes, telephone lines, satellites, location transmitters and/orbeacons, wireless network transmitters and receivers, combinationsthereof, and the like. In some embodiments, the location component 1638includes one or more sensors such as a compass, an accelerometer, and/ora gyroscope to determine the orientation of the MD 102. Using thelocation component 1638, the MD 102 can generate and/or receive data toidentify its location, or transmit data used by other devices todetermine the location of the MD 102. The location component 1638 mayinclude multiple components for determining the location and/ororientation of the MD 102.

The illustrated MD 102 also includes a power source 1640, such as one ormore batteries and/or other power subsystem (AC or DC). The power source1640 may interface with an external power system or charging equipmentvia a power I/O component 1642.

Turning now to FIG. 17, an exemplary computer architecture 1700 for acomputer system capable of executing the software components describedherein will be described in detail. The computer architecture 1700illustrates an architecture for the RNC 118 and the SGSN 126. Thecomputer architecture 1700 may be utilized to execute any aspects of thesoftware components presented herein.

The illustrated computer architecture 1700 includes a central processingunit 1702 (“CPU”), a system memory 1704, including a random accessmemory 1706 (“RAM”) and a read-only memory (“ROM”) 1708, and a systembus 1710 that couples the memory 1704 to the CPU 1702. A basicinput/output system containing the basic routines that help to transferinformation between elements within the computer architecture 1700, suchas during startup, is stored in the ROM 1708. The computer architecture1700 further includes a mass storage device 1712 for storing anoperating system 1714. The mass storage device 1712 also includes one ofthe RNC application 132 and the SGSN application 134 depending uponwhether the computer architecture 1700 is for the RNC 118 or the SGSN126.

The mass storage device 1712 is connected to the CPU 1702 through a massstorage controller (not shown) connected to the bus 1710. The massstorage device 1712 and its associated computer-readable media providenon-volatile storage for the computer architecture 1700. Although thedescription of computer-readable media contained herein refers to a massstorage device, such as a hard disk or CD-ROM drive, it should beappreciated by those skilled in the art that computer-readable media canbe any available computer storage media or communication media that canbe accessed by the computer architecture 1700.

Communication media includes computer readable instructions, datastructures, program modules, or other data in a modulated data signalsuch as a carrier wave or other transport mechanism and includes anydelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics changed or set in a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared, and other wireless media. Combinations of the any of the aboveshould also be included within the scope of computer-readable media.

By way of example, and not limitation, computer storage media mayinclude volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer-readable instructions, data structures, program modules, orother data. For example, computer media includes, but is not limited to,RAM, ROM, EPROM, EEPROM, flash memory or other solid state memorytechnology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computer architecture 1700. For purposes of the claims, the phrase“computer storage medium” and variations thereof, does not includewaves, signals, and/or other transitory and/or intangible communicationmedia, per se.

According to various embodiments, the computer architecture 1700 mayoperate in a networked environment using logical connections to remotecomputers or network elements through a network such as the network 100.The computer architecture 1700 may connect to the network 100 through anetwork interface unit 1716 connected to the bus 1710. It should beappreciated that the network interface unit 1716 also may be utilized toconnect to other types of networks and remote computer systems. Thecomputer architecture 1700 also may include an input/output controller1720 for receiving and processing input from a number of other devices,including a keyboard, mouse, electronic stylus, or other input device(not shown in FIG. 17). Similarly, the input/output controller 1720 mayprovide output to a display screen, a printer, or other type of outputdevice (also not shown in FIG. 17).

It should be appreciated that the software components described hereinmay, when loaded into the CPU 1702 and executed, transform the CPU 1702and the overall computer architecture 1700 from a general-purposecomputing system into a special-purpose computing system customized tofacilitate the functionality presented herein. The CPU 1702 may beconstructed from any number of transistors or other discrete circuitelements, which may individually or collectively assume any number ofstates. More specifically, the CPU 1702 may operate as a finite-statemachine, in response to executable instructions contained within thesoftware modules disclosed herein. These computer-executableinstructions may transform the CPU 1702 by specifying how the CPU 1702transitions between states, thereby transforming the transistors orother discrete hardware elements constituting the CPU 1702.

Encoding the software modules presented herein also may transform thephysical structure of the computer-readable media presented herein. Thespecific transformation of physical structure may depend on variousfactors, in different implementations of this description. Examples ofsuch factors may include, but are not limited to, the technology used toimplement the computer-readable media, whether the computer-readablemedia is characterized as primary or secondary storage, and the like.For example, if the computer-readable media is implemented assemiconductor-based memory, the software disclosed herein may be encodedon the computer-readable media by transforming the physical state of thesemiconductor memory. For example, the software may transform the stateof transistors, capacitors, or other discrete circuit elementsconstituting the semiconductor memory. The software also may transformthe physical state of such components in order to store data thereupon.

As another example, the computer-readable media disclosed herein may beimplemented using magnetic or optical technology. In suchimplementations, the software presented herein may transform thephysical state of magnetic or optical media, when the software isencoded therein. These transformations may include altering the magneticcharacteristics of particular locations within given magnetic media.These transformations also may include altering the physical features orcharacteristics of particular locations within given optical media, tochange the optical characteristics of those locations. Othertransformations of physical media are possible without departing fromthe scope and spirit of the present description, with the foregoingexamples provided only to facilitate this discussion.

In light of the above, it should be appreciated that many types ofphysical transformations take place in the computer architecture 1700 inorder to store and execute the software components presented herein. Itis also contemplated that the computer architecture 1700 may not includeall of the components shown in FIG. 17, may include other componentsthat are not explicitly shown in FIG. 17, or may utilize an architecturecompletely different than that shown in FIG. 17.

Based on the foregoing, it should be appreciated that technologies forselective establishment of radio access bearers to support simultaneousvoice and data communications in a mobile telecommunications networkhave been disclosed herein. Although the subject matter presented hereinhas been described in language specific to computer structural features,methodological and transformative acts, specific computing machinery,and computer readable media, it is to be understood that the inventiondefined in the appended claims is not necessarily limited to thespecific features, acts, or media described herein. Rather, the specificfeatures, acts and mediums are disclosed as example forms ofimplementing the claims.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Various modifications andchanges may be made to the subject matter described herein withoutfollowing the example embodiments and applications illustrated anddescribed, and without departing from the true spirit and scope of thepresent invention, which is set forth in the following claims.

What is claimed is:
 1. A computer-readable storage medium storinginstructions that, when executed by a processor of a mobile device,cause the processor to perform operations comprising: receiving aselection of a voice prioritized option; establishing, over a voice-onlyradio access bearer, a voice session with another device; collecting,during at least a portion of the voice session, uplink transmit powerstatistics associated with maintaining the voice session; calculating amean uplink transmit power from the uplink transmit power statistics;calculating a standard deviation from the uplink transmit powerstatistics; calculating a value for the mean uplink transmit power plusthe standard deviation; receiving a data request; determining if thevalue calculated for the mean uplink transmit power plus the standarddeviation at least meets a threshold value of uplink transmit power thatis insufficient for the mobile device to support a multiple radio accessbearer, wherein the multiple radio access bearer simultaneously supportsboth a voice component of the voice session and a data component of thedata request; in response to determining that the value does not atleast meet the threshold value, allowing establishment of the multipleradio access bearer, transferring the voice session to the multipleradio access bearer, and tearing down the voice-only radio accessbearer; and in response to determining that the value does at least meetthe threshold value, denying establishment of the multiple radio accessbearer.
 2. The computer-readable storage medium of claim 1, wherein theoperations further comprise displaying, on a display of the mobiledevice, the voice prioritized option in context of a first selectablegraphical user interface element, and wherein receiving the selection ofthe voice prioritized option comprises receiving the selection of thevoice prioritized option via the first selectable graphical userinterface element.
 3. The computer-readable storage medium of claim 2,wherein the voice prioritized option is identified as a maximize voicecoverage option.
 4. The computer-readable storage medium of claim 2,wherein the operations further comprise displaying, on the display ofthe mobile device, a voice only option in context of a second selectablegraphical user interface element.
 5. The computer-readable storagemedium of claim 4, wherein the operations further comprise displaying,on the display of the mobile device, a normal option in context of athird selectable graphical user interface element.
 6. Thecomputer-readable storage medium of claim 2, wherein the operationsfurther comprise displaying, on the display of the mobile device, anormal option in context of a second selectable graphical user interfaceelement.
 7. The computer-readable storage medium of claim 2, wherein thefirst selectable graphical user interface element is part of a settingsapplication, a dialer application, or a software widget.
 8. Thecomputer-readable storage medium of claim 1, wherein the threshold valueof uplink transmit power comprises a percentage of a maximum uplinktransmit power.
 9. The computer-readable storage medium of claim 1,wherein the operations further comprise adjusting the threshold valuedepending upon a radio condition.
 10. The computer-readable storagemedium of claim 1, wherein receiving the selection of the voiceprioritized option comprises receiving the selection of the voiceprioritized option prior to the voice session being established, duringestablishment of the voice session, during the voice session, or afterthe voice session.
 11. The computer-readable storage medium of claim 1,wherein the computer-readable medium comprises a firmware.
 12. Acomputer-readable storage medium storing instructions that, whenexecuted by a processor of a mobile device, cause the processor toperform operations comprising: presenting, on a display of the mobiledevice, a network settings graphical user interface comprising an inputportion and a settings control options portion, the settings controloptions portion comprising a control settings remotely option; receivinga selection of the control settings remotely option; based uponreceiving the selection of the control settings remotely option,receiving, from a server, a threshold value for a voice prioritysetting, wherein establishment of a multiple radio access bearer tosimultaneously support both a voice component of a voice session and adata component of a data request is denied when the voice session isestablished and when a value associated with maintaining the voicesession at least meets the threshold value; storing the threshold valuefor the voice priority setting in the input portion of the networksettings graphical user interface; establishing, over a voice-only radioaccess bearer, the voice session with another device; collecting, duringat least a portion of the voice session, uplink transmit powerstatistics for the mobile device associated with maintaining the voicesession; calculating a mean uplink transmit power from the uplinktransmit power statistics; calculating a standard deviation from theuplink transmit power statistics; calculating a value for the meanuplink transmit power plus the standard deviation; receiving the datarequest; determining if the value calculated for the mean uplinktransmit power plus the standard deviation at least meets the thresholdvalue; in response to determining that the value for the mean uplinktransmit power plus the standard deviation does not at least meet thethreshold value, allowing establishment of the multiple radio accessbearer, transferring the voice session to the multiple radio accessbearer, and tearing down the voice-only radio access bearer; and inresponse to determining that the value for the mean uplink transmitpower plus the standard deviation does at least meet the thresholdvalue, denying establishment of the multiple radio access bearer. 13.The computer-readable storage medium of claim 12, wherein the inputportion of the network settings graphical user interface comprises athreshold input box and the voice priority setting comprises a thresholdsetting.
 14. The computer-readable storage medium of claim 13, whereinthe threshold setting is a maximum uplink power threshold setting andthe threshold value is a particular maximum uplink power that, when atleast met, causes the mobile device to deny data requests.
 15. Thecomputer-readable storage medium of claim 13, wherein the thresholdsetting and the threshold value are associated with a received signalcode power, a ratio of a received energy and an interference level, acarrier-to-noise ratio, or a received signal strength indicator.
 16. Thecomputer-readable storage medium of claim 12, wherein the server isoperated by a service provider that is capable of providing a dataservice that supports data access for the mobile device.
 17. Thecomputer-readable storage medium of claim 12, wherein the operationsfurther comprise: receiving, from the server, an adjusted thresholdvalue based upon a radio condition known to the server; and replacingthe value for the voice priority setting in the input portion of thenetwork settings graphical user interface with the adjusted thresholdvalue.
 18. The computer-readable storage medium of claim 12, wherein thecomputer-readable storage medium comprises a firmware.
 19. Acomputer-readable storage medium storing instructions that, whenexecuted by a processor of a mobile device, cause the processor toperform operations comprising: presenting, on a display of the mobiledevice, a voice prioritized option in context of a first selectablegraphical user interface element, wherein the voice prioritized optiondenies establishment of a multiple radio access bearer to simultaneouslysupport both a voice component of a voice session and a data componentof a data request when the voice session is established and when a valueassociated with maintaining the voice session at least meets a thresholdvalue; presenting, on the display of the mobile device, a voice onlyoption in context of a second selectable graphical user interfaceelement, wherein the voice only option denies the data request when thevoice session is established, whether or not the value associated withmaintaining the voice session at least meets the threshold value;presenting, on the display of the mobile device, a normal option incontext of a third selectable graphical user interface element, whereinthe normal option allows establishment of the multiple radio accessbearer to simultaneously support both the voice component of the voicesession and the data component of the data request when the voicesession is established; whether or not the value associated withmaintaining the voice session at least meets the threshold value,receiving a selection of the voice prioritized option via the firstselectable graphical user interface element; establishing, over avoice-only radio access bearer, the voice session with another device;collecting, during at least a portion of the voice session, uplinktransmit power statistics for the mobile device associated withmaintaining the voice session; calculating a mean uplink transmit powerfrom the uplink transmit power statistics; calculating a standarddeviation from the uplink transmit power statistics; calculating a valuefor the mean uplink transmit power plus the standard deviation;receiving the data request; determining if the value calculated for themean uplink transmit power plus the standard deviation at least meetsthe threshold value; in response to determining that the value for themean uplink transmit power plus the standard deviation does not at leastmeet the threshold value, allowing establishment of the multiple radioaccess bearer, transferring the voice session to the multiple radioaccess bearer, and tearing down the voice-only radio access bearer; andin response to determining that the value for the mean uplink transmitpower plus the standard deviation does at least meet the thresholdvalue, denying establishment of the multiple radio access bearer. 20.The computer-readable storage medium of claim 19, wherein thecomputer-readable storage medium comprises a firmware.